-
-
Notifications
You must be signed in to change notification settings - Fork 320
test: rename fixture config to default_config to avoid name conflict #1836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files☔ View full report in Codecov by Sentry. |
a2166d7 to
12e529a
Compare
12e529a to
79ce43e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duplicated fixtures
79ce43e to
50ea789
Compare
noirbizarre
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think just remove the duplicate config fixture in tests/commands/conftest.py is enough.
I find config more explicit and producing shorted line that default_config (for which I would expect a non-default config somewhere).
Plus, pytest fixture pattern philosophy push to reuse names to override fixture instead of multiplicating fixture, so I think it's best to just keep config
|
Thanks for explanation, I didn't know the philosophy details behind pytest fixture. The main motivation of this PR was that we have a module called Now I agree that we should keep the name unchanged. |
|
I will close this PR and make create another one for removing duplicated fixtures. |
No description provided.